-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(bin)!: Remove release supporting tools #44
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly cleanup and removing stuff when looking at the relevant commit. However I would still rebase the whole branch and drop the extra two commits. They should already be on next
.
Yes, I need to. I did some force-pushes to |
f95606e
to
839f63f
Compare
- lerna is now used for the release process including changelogs
839f63f
to
caf0bf3
Compare
- remove docs for the removed bin commands - update info on PRs and releasing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for a all the nice doc updates 👍
I cannot self-approve though...
* feat(bin)!: Remove release supporting tools - lerna is now used for the release process including changelogs * docs: Cleanup outdated docs - remove docs for the removed bin commands - update info on PRs and releasing Co-authored-by: Jiri Vejmola <[email protected]>
We are now using Lerna and considering another existing alternative. Using our own inferior release tool seems to be pointless.